Methods and systems for authorizing imaging device concurrent account use

ABSTRACT

Embodiments of the present invention comprise systems, methods and devices for allowing a plurality of concurrent users to use a single imaging device account.

RELATED REFERENCES

This application is a continuation-in-part of U.S. patent applicationSer. No. 10/962,248, entitled “Methods and Systems for Imaging DeviceRemote Application Interaction, filed on Nov. 8, 2004; this applicationis also a continuation-in-part of U.S. patent application Ser. No.10/961,793, entitled “Methods and Systems for Imaging Device Remote FormManagement, filed on Nov. 8, 2004; this application is also acontinuation-in-part of U.S. patent application Ser. No. 10/961,911,entitled “Methods and Systems for Imaging Device Remote LocationFunctions, filed on Nov. 8, 2004; this application is also acontinuation-in-part of U.S. patent application Ser. No. 10/961,594,entitled “Methods and Systems for Imaging Device Remote documentManagement, filed on Nov. 8, 2004; and this application is also acontinuation-in-part of U.S. patent application Ser. No. 10/962,103,entitled “Methods and Systems for Imaging Device Document Translation,filed on Nov. 8, 2004; this application also claims the benefit of U.S.Provisional Patent Application No. ______, entitled “Methods and Systemsfor Imaging Device Applications,” filed Jul. 28, 2005.

FIELD OF THE INVENTION

Embodiments of the present invention comprise methods and systems forimaging device accounting and in particular, concurrent use of anaccount by multiple users.

BACKGROUND

Imaging devices such as printers, copiers, scanners and fax machines canhave a wide array of functions and capabilities to fit specific uses orcombinations of uses. Imaging devices often take the form of amulti-function peripheral device (MFP) that combines the functions oftwo or more of the traditionally separated imaging devices. An MFP maycombine any number of imaging devices, but typically comprises thefunctions of a printer, scanner, copier and fax machine.

Some imaging devices may contain computing resources for data storageand processing such as processors, hard disk drives, memory and otherdevices. As imaging devices add more features and functions, they becomemore costly and complex.

More complex imaging devices and MFPs may comprise network connectivityto provide communication with other computing devices, such as personalcomputers, other imaging devices, network servers and other apparatus.This connectivity allows the imaging device to utilize off-boardresources that are available on a connected network.

Imaging devices typically have a user input panel with an array ofbuttons, knobs and other user input devices. Some devices also have adisplay panel, which can be for display only or can be a touch paneldisplay that enables user input directly on the display.

Devices with touch panel displays or displays with buttons arranged incooperation with the display can display menu data that may be selectedby user input. This menu data is typically driven by an on-board servermodule within the imaging device.

BRIEF SUMMARY OF THE INVENTION

Embodiments of the present invention comprise systems, methods anddevices for allowing concurrent users to log onto the same imagingdevice account. In some embodiments this function is enabled throughcalculation of job charges and application of job charges to an accountprior to execution of the job.

The foregoing and other objectives, features, and advantages of theinvention will be more readily understood upon consideration of thefollowing detailed description of the invention taken in conjunctionwith the accompanying drawings.

BRIEF DESCRIPTION OF THE SEVERAL DRAWINGS

FIG. 1 is a diagram of an embodiment of the present invention comprisingan imaging device in connection with a remote computing device;

FIG. 2 is an image of an exemplary user interface for an imaging device;

FIG. 3 shows an exemplary imaging device;

FIG. 4 is a chart depicting steps of an imaging device method;

FIG. 5 is a chart depicting steps of an imaging device method using amarkup language;

FIG. 6 shows an exemplary remote computing device embodiment;

FIG. 7 is a diagram showing components of an exemplary remote computingdevice;

FIG. 8 is a chart showing steps of a remote computing device method;

FIG. 9 is a chart showing steps of a remote computing device methodusing a markup language;

FIG. 10 is a diagram showing a system comprising multiple imagingdevices in connection with a remote computing device;

FIG. 11 is a chart showing steps of a method comprising RCD processingof user input data;

FIG. 12 is a diagram showing components of some embodiments comprisinglinked resources;

FIG. 13 is a diagram showing components of some embodiments comprisinglinked resources and multiple imaging devices;

FIG. 14 is a chart showing the steps of a method of some embodimentscomprising accounting authorization and application of job charges to auser account prior to job execution;

FIG. 15 is a chart showing the steps of a method of some embodimentscomprising accounting authorization, application of job charges to auser account prior to job execution and automatic job modification;

FIG. 16 is a chart showing the steps of a method of some embodimentscomprising accounting authorization, application of job charges to auser account prior to job execution and user prompting for jobmodification;

FIG. 17 is a chart showing the steps of a method of some embodimentscomprising concurrent user authorization, accounting authorization andapplication of job charges to a user account prior to job execution;

FIG. 18 is a chart showing the steps of a method of some embodimentscomprising concurrent user authorization, accounting authorization,application of job charges to a user account prior to job execution andautomatic job modification;

FIG. 19 is a chart showing the steps of a method of some embodimentscomprising concurrent user authorization, accounting authorization,application of job charges to a user account prior to job execution anduser prompting for job modification;

FIG. 20 is a chart showing the steps of a method of some embodimentscomprising accounting authorization, application of job charges to auser account prior to job execution and post-commencement reassessmentof job charges;

FIG. 21 is a chart showing the steps of a method of some embodimentscomprising accounting authorization, automatic job modification,application of job charges to a user account prior to job execution andpost-commencement reassessment of job charges;

FIG. 22 is a chart showing the steps of a method of some embodimentscomprising accounting authorization, user prompting for jobmodification, application of job charges to a user account prior to jobexecution and post-commencement reassessment of job charges;

FIG. 23 is a chart showing the steps of a method of some embodimentscomprising concurrent user authorization, accounting authorization,application of job charges to a user account prior to job execution andpost-commencement reassessment of job charges;

FIG. 24 is a chart showing the steps of a method of some embodimentscomprising concurrent user authorization, accounting authorization,automatic job modification, application of job charges to a user accountprior to job execution and post-commencement reassessment of jobcharges; and

FIG. 25 is a chart showing the steps of a method of some embodimentscomprising concurrent user authorization, accounting authorization, userprompting for job modification, application of job charges to a useraccount prior to job execution and post-commencement reassessment of jobcharges.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Embodiments of the present invention will be best understood byreference to the drawings, wherein like parts are designated by likenumerals throughout. The figures listed above are expressly incorporatedas part of this detailed description.

It will be readily understood that the components of the presentinvention, as generally described and illustrated in the figures herein,could be arranged and designed in a wide variety of differentconfigurations. Thus, the following more detailed description of theembodiments of the methods and systems of the present invention is notintended to limit the scope of the invention but it is merelyrepresentative of the presently preferred embodiments of the invention.

Elements of embodiments of the present invention may be embodied inhardware, firmware and/or software. While exemplary embodiments revealedherein may only describe one of these forms, it is to be understood thatone skilled in the art would be able to effectuate these elements in anyof these forms while resting within the scope of the present invention.

Embodiments of the present invention comprise interfaces andarchitecture that integrate imaging devices with remote computing deviceapplications and environments to provide solutions that may not bepossible solely with an imaging device alone. Some embodiments comprisean infrastructure and set of interfaces that allow applications on anetwork to programmatically control imaging device functions andinteract with a user through an imaging device input panel. Softwarefunctions that are not practical within the imaging device can beperformed on the server but are accessible from the imaging device.

For the purposes of this specification and claims, an imaging device(IDev) may be described as a device that performs an imaging function.Imaging functions comprise scanning, printing, copying, imagetransmission (sending and receiving), image conversion and otherfunctions. Exemplary imaging devices comprise printers, copiers,facsimile machines, scanners, computing devices that transmit, convertor process images and other devices. An IDev may also perform multipleimaging functions. For example, and not by way of limitation, amulti-function peripheral device (MFP), which typically has thecapability to perform a plurality of functions comprising a printer,scanner, copier and/or a facsimile machine or imagetransmitter/receiver, is a type of imaging device. Other MFP imagingdevices may comprise other combinations of functions and still qualifyas an IDev.

For the purposes of this specification and claims, a remote computingdevice (RCD) is a device capable of processing data and communicatingwith other devices through a communications link. An RCD is a remotedevice because it requires a communications link, such as a networkconnection, a telephone line, a serial cable or some other wired orwireless link to communicate with other devices such as an imagingdevice. Some exemplary RCDs are network servers, networked computers andother processing and storage devices that have communications links.

Some embodiments of the present invention may be described withreference to FIGS. 1 & 2. These embodiments comprise an imaging device(IDev) 4 that may be a multi-function peripheral device (MFP) or asingle function device. The imaging device 4 further comprises a userinterface (UI) panel 2, which may comprise input buttons 14 and adisplay device 12 or may comprise a touch panel system with or withoutbuttons 14. User input and display may also be performed through aseparate UI device 8, which may be connected to the imaging device 4 bya communication link 12, such as a USB connection, a network cable, awireless connection or some other communications link. UI device 8 maycomprise an input device, such as a keyboard or buttons as well as adisplay device, which may also be a touch screen panel. UI device 8 mayalso comprise an interface for transfer of instructions that are inputto the device 8 from a remote input device. This form of UI device 8 maycomprise memory sticks, USB memory cards and other storage devices thatmay be configured to store input for transfer to an imaging device.

These embodiments further comprise a remote computing device (RCD) 6that is linked to the imaging device 4 via a communications link 10,such as a network connection. This network connection may be a typicalwired connection or a wireless link.

Embodiments of the present invention may provide menu data from the RCD6 to the imaging device UI panel 2 or remote panel 8 via the networkconnection 10. Once this menu data is fed to the imaging device 4, an UIpanel 2, 8 on the imaging device 4 may be used to interact withapplications that run on the remote computing device 6. User inputreceived from UI panels 2, 8 may be returned directly to the remotecomputing device 6.

A Web Service is a software application identified by a Uniform ResourceIdentifier (URI), whose interfaces and binding are capable of beingdefined, described and discovered by Extensible Markup Language (XML)artifacts and that supports direct interactions with other softwareapplications using XML based messages via Internet-based protocols.

An application on the remote computing device 6 may use one or more WebServices to control various features in the imaging device 4, such asenabling, disabling or setting device values or controlling devicefunctions.

Embodiments of the present invention allow network applications runningon remote computing devices to interact with the user of the imagingdevice through the imaging device I/O panel. These embodiments allowimaging device user interface (UI) control (i.e., touch panel,button/display) by applications. Some embodiments may also integratecustom display screens or menus with the native imaging device UI.Embodiments may hand off control of imaging device functions betweenstandard operation modes performed on the imaging device in response touser input to an imaging device UI and open systems modes that utilizenetwork resources, such as applications on RCDs, through user input atthe imaging device UI.

Embodiments of the present invention comprise network-based applicationsthat have full control over the imaging device UI to display text andgraphics in any format. In these embodiments, the application canprogrammatically display buttons, textboxes, graphics, etc. in anylayout desired.

In some embodiments, the UI layout is easy to program using a standardlanguage, such as a markup language. These languages comprise HypertextMarkup Language (HTML), Extensible Markup Language (XML), WirelessMarkup Language (WML), Extensible Hypertext Markup Language (XHTML) andother languages.

In some embodiments of the present invention a remote computing deviceapplication or server application is able to request a keyboard UI to bedisplayed on the imaging device display 12, 8. In some embodiments, thisfunctionality is available on the imaging device and does not need to berecreated by remote computing device applications. In some embodiments,the remote computing device may define the keyboard prompt and defaultvalues. These embodiments may comprise a remote computing device that isable to rename imaging device UI buttons, such as the OK and Cancelbuttons as well as define additional buttons.

In some embodiments, menu templates may be served to the imaging deviceUI by the imaging device itself 4 or from a remote computing device 6.

External Authorization Application

Some embodiments of the present invention may comprise a remotecomputing device application that is registered as the ExternalAuthorization server. The External Authorization application may controlaccess to the imaging device and may have top-level control of the UI.UI control may be given to this application in the same manner thatcontrol is given to an internal auditor.

In these embodiments, when an imaging device system boots, it checks tosee if an External Authorization application is registered. If so, theimaging device is placed in disabled mode and the application iscontacted to take control of the UI. If the External Authorizationserver is not available, an error message may be displayed and thedevice may remain disabled. The imaging device may periodically try tocontact the External Authorization server until it is available. Table 1below describes what entity has control of the UI, in an exemplaryembodiment, when the device is in a disabled state. TABLE 1 UI Controlin Disabled State Indicator Button Press UI Control Lights Device bootsExternal Application None Document Filing External Application NoneImage Send External Application None Copy External Application None JobStatus Device - standard Job Status screens Job Status Custom SettingsDevice - standard Custom Settings N/A screens OS Mode Not available whendevice is disabledRemote Computing Device Applications

In embodiments of the present invention, access to the custom UI panelsof imaging devices may vary from application to application. Somesolutions, such as Document Management integration, may wish to leveragethe native Image Send screens, but display some custom UI's to gatheradditional information about a scan job. Other solutions, like customprinting applications, may be accessed from a separate mode than thenative functions.

In order to accommodate the diversified needs of these solutionsapplications, embodiments may support multiple integration points for UIcontrol. These integration points are based on a user action (“trigger”)for which applications may register. In some embodiments, applicationsmay be registered with target devices so that the device knows that when“trigger A” occurs on the front panel to contact “remote computingdevice B” for instructions. In exemplary embodiments, applications maybe integrated with an imaging device at any of several “trigger” points.

Remote computing devices may be registered to a specific function andcontacted when that function's hardware key is pressed (e.g. Image Send)on the imaging device UI. Any UI information provided by the remotecomputing device may be displayed instead of the standard functionscreens native to the imaging device. This trigger may be used forapplications that wish to replace the existing functions with completelycustom UI's, such as an alternative scan solution or a specializeddisplay, such as a “Section 508” compatible screen or otherspecialized-need interface that may have large buttons or otheraccommodations.

In some embodiments, each function on the imaging device may have a menuon the touch screen that remote computing devices, such as servers, canregister. This enables solutions applications to provide custom contentand still use some of the standard functionality provided by the imagingdevice. When a button assigned to a custom application is selected, amenu will be displayed with the solutions registered to that function.Users may select the desired solution and the remote computing devicewill be contacted for instructions.

In some embodiments, a stand-alone RCD mode that provides remotecomputing device application access can be accessed from the job queueportion of the UI that is displayed on every screen. This trigger pointmay be used for applications that do not fit within one of the standarddevice functions, such as custom printing solutions on an imagingdevice. When the RCD menu is selected, a menu will be displayed with thesolutions applications registered to the generic RCD mode. Users willselect the desired solution and the remote computing device will becontacted for instructions.

Hardware Key Interaction

In some embodiments of the present invention, when an imaging device isenabled, additional hardware keys may be used to manage the device.Hardware key assignments for an exemplary embodiment are shown in table2. TABLE 2 Exemplary Hardware Key Assignments Button Press Standard IDevMode RCD Mode Mode keys (Copy, Clear current job Clear current job DocFiling, Image settings, move to settings, move to Send) and Customtarget screen target screen Settings key Job Status key Move to JobStatus, Move to Job Status, maintain current maintain current settings &UI settings & UI location location Clear (C) Clears settings Sends clearevent to external application Clear All (CA) Clears settings, Cancelsjob and cancels job, and returns to default returns to default IDevscreen IDev screen (notification sent to external application) **WhenExternal Authorization is controlling the UI, only notification is sentStart Initiates scan Initiates scan function function Number keys Inputfor copy Not used count or fax numbers * Logs user out Logs user out(disable device (disable device and contact External and contactExternal Authorization for Authorization for screens) screens)

In some embodiments, in addition to the * key for logout, a timeoutperiod may be implemented. Some embodiments also comprise an auto clearsetting that can be configured for a given period of time, such as 10 to240 seconds (or disabled). In these embodiments, when there is noactivity for the time configured in auto clear, the device mayautomatically return to disabled mode and attempt to contact a remotecomputing device to retake control of the UI.

Error & Jam Notifications

Depending on a particular solution, a remote computing deviceapplication may have full or only partial control of the imaging deviceUI and a particular imaging job. In some embodiments, partial controlmay include cases where a remote computing device is monitoring clicks,but native modes are responsible for the UI interaction and controllingthe job. Partial control may also include cases where the remotecomputing device application is integrated with a native mode (UItrigger=function custom menu). In these embodiments, the imaging devicemay handle all error and jam notifications with only a notification sentto the relevant remote computing device application.

For some embodiments, in cases where the remote computing deviceapplication has full control over the UI and the job, error and jamnotifications may be handled differently depending on the type of error.For recoverable errors, a notification may be sent to the remotecomputing device application and the application may be responsible fordisplaying messages and resolving the error. For non-recoverable errors,the imaging device and RCD mode may interact to gracefully handle theerror condition (e.g. provide user with instructions for clearing jam).

Control Handoffs

In some embodiments, at different points throughout an imaging job,several applications may need control over an imaging device including,but not limited to, an External Authorization application, a standardRCD application, an imaging device native mode and other applications.The following section describes, for an exemplary embodiment, thevarious steps in an exemplary job, the entities that may have controlduring each step, and what type of control may be allowed.

Step 1: User provides credentials to access the device at the device UI.This step may be controlled by a remote computing device, such as anExternal Authorization application or by Internal Accounting (nativemode) in the imaging device itself. At the end of this step, the deviceis enabled. The External Authorization application may also specifydefault parameters or disable specific job parameters (e.g. default fileformat is PDF, but user may change; color mode is set to B/W and usermay not change).

Step 2: User sets parameters for the job using one of the native imagingdevice modes or a standard RCD application. At the end of this step theuser makes an input to initiate the job. When the input is made, anoptional notification may be sent to the standard RCD application, whichcan then change job parameters if desired. An e-mail application is oneexample of an application that may request notification when the userinput is made. A user may use native Image Send screens or other inputto select scan options and choose e-mail recipients. A user may thenselect a custom application button and choose the scan-to-e-mail optionfrom the menu. The e-mail application may then display custom screensfor the user to set permissions for the file. Once a user places theoriginal document(s) on the scanner and initiates the process, thee-mail application may capture the destination parameters set by theuser and change the target destination to the e-mail application FTPserver. The e-mail application may then receive the file, apply theappropriate permissions, and send to the e-mail recipients selected bythe user. A remote computing device application may also want to retakecontrol of the UI at this point, if, as in some embodiments, theapplication generates thumbnails of the scanned images and displays themto the user for verification.

Step 3: Once the job is initiated, the imaging device is responsible forscanning or RIPing the job and spooling it to the HDD. If the imagingdevice is configured to authorize jobs with an external authorizationapplication, it may send a click report to the application and wait forinstructions. The external authorization application may enable the jobfor sending/printing, cancel the job, or change job parameters (and thenenable). As an example, a rules-based printing application may wish tochange job parameters after it receives a click report. Some rules-basedprinting applications support rules-based printing and scanning that canlimit what each user is allowed to do based on the time of day, thedestination, or many other parameters. For example, only users in themarketing group may be able to scan high-quality color images. If a userfrom another group selects color and 600 dpi, a rules-based applicationmay change the parameters to color and 200 dpi. At the end of this stepthe job should either be authorized or canceled.

Step 4: In some embodiments, this may be an optional step, where thestandard RCD application in step 2 may have specified the destination asa HDD for temporary storage. This step may also be used, in someembodiments, by a Java application running on the imaging device. Forexample, a government office may have a custom encryption applicationrunning on the device that takes the scanned document, encrypts it, andthen requests the imaging device to send it to the target destinationselected by the user in step 2. In some embodiments, it may bebeneficial to send a notification to the external authorizationapplication after this step—because the imaging device does not know howlong the file will be on the HDD or what the application is going to dowith it—and after the send/print step.

Step 5: In the final step, the file is actually output. In typicalembodiments, the file is either sent over the network or printedlocally. At the end of this step, a notification that the job wassuccessfully completed should be sent to the external authorizationapplication and optionally, to the standard RCD application.

Device Control and Management API's

The API's may be used to allow a remote computing device application tocontrol access to an imaging device for vend applications and to managethe device from a remote location.

Device Control and Vend API

In some embodiments of the present invention, a Device Control and VendAPI allows applications to enable and disable access to the device andtrack click counts. The Device Control and Vend API may provide an RCDwith the following controls:

Enable/disable device of function—this may allow an RCD to enable ordisable access to the device as a whole or by function to enforceindividual user privileges. In some exemplary embodiments, the functionslisted in Table 3 may be selectively enabled or disabled by anapplication. TABLE 3 Device Functions Enable/Disable Description CopyCopy function (Copy button) Image Send Scan and fax function, plus sendfrom Doc Filing (Image Send button) Document Filing All access toDocument Filing functions (Document Filing button) Print Network prints,pull print from front panel, and print from Document Filing (No buttoncontrol)

Report clicks used—at the end of a successful job, the clicks used maybe reported back to an RCD including: TABLE 4 Job and PageCharacteristics Fax PC- E-mail/ Broad- Scan Item Copy Print Send Fax FTPcast to HD JOB Characteristics Job Mode Yes Yes Yes Yes Yes Yes YesBroadcast No No Yes Yes Yes Yes No Manage No. User Name Yes Yes Yes YesYes Yes Yes Address No No Yes Yes Yes # No Start Time Yes Yes Yes YesYes Yes Yes End Time Yes Yes Yes Yes Yes Yes Yes Total Page Yes Yes YesYes Yes Yes Yes Result Yes Yes Yes Yes Yes Yes Yes Error Cause No No YesYes Yes Yes No Doc Filing Yes Yes Yes Yes Yes Yes Yes Save Mode *1 *1 *1*1 *1 *1 *1 File Name *1 Yes *1 Yes Yes *1 Yes File Size Yes Yes *1 *1*1 *1 Yes Resolution Yes Yes Yes Yes Yes Yes Yes Special Yes Yes Yes NoYes Yes Yes Finishing Yes Yes No No No No No File Format No No No No YesYes No Compression No No No No Yes Yes No PAGE Characteristics Copy YesYes Yes Yes Yes # Yes Paper Size Yes Yes Yes Yes Yes Yes YesSimplex/duplex Yes Yes Yes Yes Yes Yes Yes Paper Type Yes Yes Yes Yes NoNo Yes Page Yes Yes Yes Yes Yes Yes Yes*1 - Yes when Document Filing is used

Debit mode—in these embodiments, when an application enables the deviceit may specify if the current job requires authorization. If so, the jobwill be spooled to memory and click information (e.g., as defined inTable 4) will be sent to an RCD. An RCD will then notify the device ifthe job should be deleted or output/sent. At this point, the applicationalso has the option of changing job parameters. If the application doesnot require authorization, the job will continue as normal and a clickreport will be sent at the end of the job.

Print job accounting—in these embodiments, an RCD may wish to monitorprint jobs along with walk-up functions. For print job accounting, anIDev may monitor all incoming print jobs and send accounting data in thePJL header to an RCD for verification before printing the job. The RCDwill evaluate the accounting data (or lack thereof) and inform the IDevto continue with or cancel the job.

Report on unidentified jobs—in these embodiments, an RCD may also wishto monitor print jobs that it cannot associate to a specific user, suchas device reports and incoming fax jobs. The RCD can register to receiveclick counts for all unidentified jobs, so that it may bill them to ageneral account.

Device Management API

In some embodiments of the present invention, a Device Management APIallows a network application to remotely setup and manage the imagingdevice. In exemplary embodiments, the Device Management API may providean RCD with the following controls:

-   -   Device status—an RCD may request the current status of the        device. This is the same status information as reported on the        embedded web pages.    -   Device configuration—an RCD can retrieve a list of installed        options supported by the device.    -   Web Page settings—an RCD application can retrieve and set any of        the values that are configurable on the embedded web pages.    -   Key Operator Programs—an RCD application can retrieve and set        any of the values that are configurable in Key Operator        Programs, including software keys.    -   Custom Settings—an RCD application can retrieve and set any of        the values that are configurable in Custom Settings.    -   Job Status—an RCD application can retrieve the current job queue        and history information and reprioritize or delete jobs in the        queue.    -   Click counts—an RCD application can retrieve device total counts        and clicks for each function by account code.    -   Data Security settings—an RCD application may retrieve the        status information on the DSK (e.g. last erase) and initiate        data clear functions.    -   RED data—an RCD can retrieve all data typically sent in a RED        message.    -   Remote reboot—an RCD can initiate a reboot of the imaging        device.

The above groupings are provided only as an exemplary embodimentdetailing which settings should be included. In some embodiments, actualAPI's should be grouped by functional areas since there may be overlapbetween Key Operator settings and web page settings.

Internal Accounting API

In some embodiments, an Internal Accounting API may allow a remotecomputing device application to configure internal accounting and reportclick counts. In some exemplary embodiments an Internal Accounting APImay include:

-   -   Set Auditing Options—an RCD may set auditing options including        which modes auditing is enabled for, “account number security”,        and “cancel jobs of invalid accounts.”    -   Manage Account Codes—an RCD can add, edit, or delete account        codes    -   Account Limits—an RCD application can specify a maximum number        of clicks by function for individual account codes or for all        account codes    -   Account Reset—an RCD application can reset the click count for        an individual account or for all accounts    -   Retrieve Clicks—an RCD can retrieve the number of clicks by        function for each account code        Font and Form Management API

Some embodiments of the present invention may comprise a Font and FormManagement API, which allows an RCD application to remotely download andmanage fonts and forms in mass-storage. In some exemplary embodiments, aFont and Form Management API may provide a remote computing device withthe following controls:

-   -   Mass storage control—an RCD application can retrieve mass        storage status information including storage capacity, space        available, and write-protect mode plus modify write-protect        status.    -   Resource list—an RCD application can retrieve a list of stored        fonts and forms including font or macro ID, font number,        font/form name, escape sequence, and file size.    -   Download resource—an RCD application can download PCL fonts, PCL        macros, and PS fonts and forms. Any special processing that is        performed when a resource is downloaded via the web pages will        also be performed when the resource is downloaded via Open        Systems.    -   Delete resource—an RCD application can delete any resource        stored in mass storage.    -   Upload resources—an RCD application can upload an individual or        all resources. On devices where effective memory management is        unavailable, a server application can use this function to        “defrag” mass storage.    -   Font/macro ID's—an RCD application can assign or modify the ID's        assigned to PCL fonts and macros.        Firmware Management API

In some embodiments of the present invention, a Firmware Management APImay allow a remote computing device or network application to remotelydownload and manage the imaging device firmware. In some exemplaryembodiments, a Firmware Management API may provide a remote computingdevice (e.g., a server) with the following controls:

-   -   Firmware versions—an RCD application can retrieve the current        firmware version numbers.    -   Service mode—an RCD application can place the MFP in service        mode to lockout other jobs that will interfere with firmware        upgrade. Upon receiving a service mode request, the IDev will        stop accepting incoming jobs, complete all jobs in the queue,        and then notify the server that it is in service mode.    -   Update firmware—an RCD can download an updated firmware version        to the device. If a reboot is necessary, the IDev will perform        it automatically when download is complete.    -   Download status—the IDev will send a status notification        (success/error) to an RCD after firmware download.    -   Revert to previous version—if firmware update is not successful,        the application can request the IDev to revert to the previous        firmware version.

Device Function API's

In some embodiments of the present invention, device function API'sallow a remote computing device application to use existing imagingdevice functionality to provide new custom solutions.

Image Send API

In some embodiments, an Image Send API may provide the remote computingdevice application with the following controls:

-   -   Image Send Parameters—a remote computing device application can        get and set values for the following scan and fax parameters:        -   COLOR OR B/W        -   IMAGE MODE—TEXT, TEXT/PHOTO, PHOTO; EXPOSURE LEVEL        -   RESOLUTION        -   FILE FORMAT—FILE TYPE, COMPRESSION, AND PAGES PER FILE        -   ORIGINAL—ORIGINAL SIZE, SIMPLEX/DUPLEX, ROTATE, AND JOB            BUILD        -   FILENAME        -   SUBJECT        -   MESSAGE        -   SENDER        -   SCHEDULE SEND TIME        -   PAGE DIVISION (BOOK SCANNING)        -   COVER PAGE        -   TRANSMISSION MESSAGE (CONFIDENTIAL, URGENT, ETC.)        -   THIN PAPER SCANNING        -   DESTINATION        -   DOCUMENT FILING    -   Initiate Scan—the remote computing device application can        initiate the scan function (same as user pressing start button).

In some embodiments, a remote computing device can change the defaultvalues on the imaging device or the values for the current job. For thecurrent job, the remote computing device may also specify if scanparameters may be modified by the user or not. If one remote computingdevice application (e.g. Access Control) specifies that a parametercannot be changed and then a second application (e.g. DocumentManagement) tries to set the parameter, a notification may be sent tothe second application and the setting will not be changed.

Print API

In some embodiments, print jobs may be submitted by remote computingdevice applications using standard printing channels. In some exemplaryembodiments, a Print API may provide a remote computing device with thefollowing additional control:

-   -   PJL sniffing—an RCD application can register with the IDev to be        contacted for instructions when a specific PJL command is found        in a print job. The RCD can then instruct the IDev to replace        the command, cancel the job, or continue printing. This        interface may be used in applications like accounting and        other-brand compatibility.        Copy API

In some embodiments of the present invention, a Copy API may provide aremote computing device with the following exemplary controls:

-   -   Copy Parameters—an RCD application can get and set values for        the following copy parameters:        -   COLOR OR B/W        -   EXPOSURE—TEXT, TEXT/PHOTO, PHOTO, SUPER PHOTO; EXPOSURE            LEVEL        -   PAPER SELECT (BY TRAY)        -   COPY RATIO        -   2-SIDED COPY—1TO1, 1TO2, 2TO2, 2TO1; BINDING EDGE        -   OUTPUT—OUTPUT TRAY, SORT, STAPLE, GROUP, OFFSET        -   ORIGINAL SIZE        -   SPECIAL FUNCTIONS—MARGIN SHIFT, ERASE, PAMPHLET, ETC.        -   DOCUMENT FILING    -   Initiate Copy—an RCD application can initiate the copy function        (same as user pressing start button).

In some embodiments, a remote computing device can change the defaultvalues on the imaging device or the values for the current job. For thecurrent job, the remote computing device may also specify if copyparameters may be modified by the user or not.

Document Filing API

In some embodiments of the present invention, a Document Filing API mayprovide a remote computing device with the following exemplary controls:

-   -   Backup/restore—the remote computing device application can        import and export a batch file with all Document Filing data. In        some embodiments, this package will be in a proprietary format        since it contains documents that are password-protected and        should not be accessed individually—this is typically for        restore in case of failure or cloning to other devices.    -   File/folder list—the remote computing device application can        retrieve, modify, and create new files and, folders to be stored        on the IDev (also covered in device management).    -   Download file—the remote computing device can download a new        file to the Document Filing systems and specify folder,        filename, username, and password.    -   User list—the remote computing device application can retrieve,        modify, and create new users to be stored on the IDev (also        covered in device management).    -   HDD Status—the remote computing device application can retrieve        the current HDD status including the % allocated to the main        folder, quick folder, and custom folders and the % remaining.    -   Doc Filing Parameters—the remote computing device application        can get and set values for storing a file to Doc Filing        including:        -   EXPOSURE        -   RESOLUTION        -   ORIGINAL—SIZE, SIMPLEX/DUPLEX        -   FILE INFORMATION—USERNAME, FILENAME, FOLDER, CONFIDENTIAL,            PASSWORD        -   SPECIAL MODES—ERASE, DUAL PAGE COPY, 2IN1, JOB BUILD, CARD            SHOT    -   Initiate Print—the remote computing device application can        select a stored file and initiate a print including the        following parameters:        -   PAPER SIZE/SOURCE        -   OUTPUT—SORT/GROUP, OUTPUT TRAY, STAPLE, PUNCH, OFFSET        -   SIMPLEX/DUPLEX (TABLET/BOOKLET)        -   TANDEM PRINT        -   NUMBER OF COPIES        -   DELETE OR STORE AFTER PRINTING    -   Initiate Send—the remote computing device application can select        a stored file and initiate a send including the following        parameters:        -   RESOLUTION        -   FILE FORMAT        -   DESTINATION        -   TIMER        -   SENDER        -   FILENAME        -   SUBJECT        -   MESSAGE

Security

Allowing external applications to control an imaging device opens up theimaging device to new security vulnerabilities. In embodiments of thepresent invention that provide some security measures, the followingexemplary items are security concerns that may be addressed by theremote computing device interface.

Access to remote computing device interfaces may be limited to validapplications. Embodiments provide extensive access and control of theimaging device, which poses a significant security risk. The interfaceof these embodiments may be protected from access by attackers, whilemaintaining ease of setup and use for valid solutions.

Confidential data (user credentials and job data) may be protectedduring network transfer. User credentials and job data may be securedduring network transfer to ensure that it cannot be stolen, an intrudercannot monitor device activity, and a man-in-the-middle attack cannotchange messages. Imaging devices may support Secure Sockets Layer (SSL)and other connections to ensure data is safe while being communicatedbetween the imaging device and remote computing device applications.

Administrators may have the ability to lock-down imaging device access.For users with strict security policies, administrators may have theability to disable access by remote computing devices or limit access tospecific applications. Administrators may have an option to register thelimited applications that they wish to access the imaging deviceinterfaces.

Remote computing device applications may ensure the imaging device isnot being “spoofed.” The remote computing device may be able toauthenticate an imaging device that it is contract with it to ensure anintruder cannot imitate the imaging device to collect networkconfiguration and password information, monitor file/folder structuresof a document management system, or spoof security settings and DSKstatus of the imaging device.

A remote computing device may ensure that the server is not being“spoofed.” The imaging device must be able to authenticate all remotecomputing devices that it is in contact with to ensure that an intruderis not spoofing the remote computing device's IP address. By pretendingto be the remote computing device, an intruder could steal usercredentials, redirect scanned documents, change device settings orfirmware, or bring down the access control system (either to provideaccess to unauthorized users or initiate a denial of service attack forvalid users).

Access control/vend applications may not be compromised when a remotecomputing device is unavailable. When the remote computing device isunavailable, it may not be acceptable to provide open access to thedevice. If the remote computing device is unavailable at startup orbecomes unavailable at anytime (e.g. someone disconnects network cable),the imaging device may immediately be disabled and an error messagedisplayed.

An administrator may be able to adjust a security level based on companyand application requirements. Security requirements can have a largeimpact on the time it takes to develop a remote computing deviceapplication and the resources required to implement the solution. Usersusing some embodiments may range from a small business with one imagingdevice, no IT staff, and a simple scan or print application to a largegovernment office using access control and audit trails to track alldevice activity. The security measures used to protect imaging deviceinterfaces may be adjustable by the administrator to match the targetenvironment.

The imaging device and remote computing device applications may be ableto hand-off user credentials. Users may be prompted to login at multiplepoints throughout a job. For example, an access control application oraccounting application may control total device access, the imagingdevice may have user authentication enabled for Image Send, and adocument management application may require user login before showing afolder list. In many environments, all of these applications will use acommon user database. In some embodiments, it is, therefore, desirablefor the applications to pass user credentials to each other, so thateach one does not have to repeat the authentication process.

Some embodiments of the present invention may be described withreference to FIG. 3. These embodiments comprise an imaging device only,which is configured to interact with a remote computing device, such asa server through a communications link. The imaging device 30 comprisesa user interface 32, which comprises a user input device 34, such as akeypad, one or more buttons, knobs or switches or a touch-screen paneland a display 36, which may comprise user input device 34 in the form ofa touch-screen panel.

Imaging device 30 will typically be capable of performing one or moreimaging functions including, but not limited to, scanning, printing,copying, facsimile transmission (sending and receiving) and others.

These embodiments further comprise a communications link 38, which maybe a wired connection (as shown in FIG. 3) comprising a network cable, aUniversal Serial Bus (USB) cable, a serial cable, a parallel cable, apower line communication connection such as a HomePlug connection orother wired connections. Alternatively, the communications link 38 maycomprise a wireless connection, such as an IEEE 802.11(b) compliantconnection, a Bluetooth connection, an Infrared Data Association (IrDA)connection or some other wireless connection.

The operation of some imaging device embodiments may be explained withreference to FIG. 4. In these embodiments, menu data is received 40 froma remote computing device (not shown in FIG. 3), which is connected tothe imaging device 30 via the communication link 38 through a wired orwireless connection. This menu data is then displayed 42 on the imagingdevice user interface display 36. This display of remote menu data isintended to prompt a user to make an input on the user interface inputdevice 34.

Imaging devices of these embodiments are further configured to acceptinput from a user in response to a display of remote menu data andcommunicate 44 that user input to a remote computing device. In someembodiments, this user input data will be processed by a remotecomputing device. This may comprise running an application on the remotecomputing device. This processing may also comprise accessing andcommunicating data that is stored on the remote computing device.

The imaging devices of these embodiments are further configured toreceive 46 data resulting from processing the user input data. This maycomprise data generated by an application running on the remotecomputing device in response to the user input. The imaging device mayalso receive data that was stored on a remote computing device, such asa file server, in response to processing the user input.

Once the imaging device 30 has received 46 the processed data, theimaging device 30 may perform 48 a native function in response to thedata or using the data. For example, and not be way of limitation, theimaging device 30 may print a document that was stored on the remotecomputing device and modified on the remote computing device accordingto the user input. As another non-limiting example, the imaging device30 may active or enable functions (i.e., scanning, copying, printing,fax transmission) on the imaging device in response to the receipt 46 ofprocessed data.

Some, more specific, imaging device embodiments may be explained withreference to FIG. 5. In these embodiments, the imaging device 30 isconfigured to receive 50 menu data formatted in a markup language from aremote computing device. The communication link by which the menu datais communicated may be established and maintained using a HypertextTransfer Protocol (HTTP). The markup language may comprise terms fromHypertext Markup Language (HTML), Extensible Markup Language (XML),Wireless Markup Language (WML), Extensible Hypertext Markup Language(XHTML) and/or other languages.

Once the menu data is received 50, it may be displayed 52 on the imagingdevice user interface display 36. As in previously describedembodiments, the menu data is typically intended to prompt user input onimaging device user interface 32. Display 52 of the remotely-stored menudata may be accomplished with a browser application that is native tothe imaging device 30.

In these embodiments, the imaging device 30 is further configured toroute 54 user input received though its user interface 32 to a remotecomputing device. The remote computing device that receives the userinput may then run an application or otherwise process the user inputand return the results of the processing to the imaging device 30.Accordingly, the imaging device 30 is further configured to receive 56processed data from a remote computing device. In some embodiments, theimaging device 30 may perform one or more functions in response to thereceipt 56 of processed data.

Some embodiments of the present invention may be explained withreference to FIG. 6. These embodiments comprise a remote computingdevice (RCD) 60, which has a communications link 64. Communications link64 may be a wired connection (as shown in FIG. 6) comprising a networkcable, a Universal Serial Bus (USB) cable, a serial cable, a parallelcable, a powerline communication connection such as a HomePlugconnection or other wired connections. Alternatively, the communicationslink 64 may comprise a wireless connection, such as an IEEE 802.11(b)compliant connection, a Bluetooth connection, an Infrared connection,such as those defined in the Infrared Data Association (IrDA) standardor some other wireless connection. In some embodiments, RCD 60 mayfurther comprise a data storage device 62, which is typically a harddrive, but may also be an optical drive device, such as an array ofcompact disk drives, flash memory or some other storage device.

Embodiments of RCD 60 may be further described with reference to FIG. 7.In these embodiments, RCD 60 comprises a processor 72 for processingdata and running programs such as operating systems and applications.RCD 60 may further comprise memory 74, which may be in the form ofRandom Access Memory (RAM) and Read Only Memory (ROM). Generally, anyapplications processed by processor 72 will be loaded into memory 74.RCD 60 may further comprise a network interface 78, which allows RCD 60to communicate with other devices, such as an imaging device 30. In someembodiments, RCD 60 may also comprise a user interface 80, but this isnot required in many embodiments. Storage 62 may be used to storeapplications and data that may be accessed by an imaging device 30 ofembodiments of the present invention. Processor 72, memory 74, storage62, network interface 78 and, optionally, user interface 80 aretypically linked by a system bus 76 to enable data transfer between eachcomponent. Communications link 64 may couple the RCD 60 to other devicesvia network interface 78.

In some embodiments, described with reference to FIG. 8, an RCD 60 maycomprise menu data stored on storage device 62 or in memory 74. Thismenu data may be configured for display on an imaging device userinterface 32. Menu data may be stored in many formats andconfigurations. In some embodiments menu data may take the form of termsexpressed with a markup language. The markup language may comprise termsfrom Hypertext Markup Language (HTML), Extensible Markup Language (XML),Wireless Markup Language (WML), Extensible Hypertext Markup Language(XHTML) and/or other languages. In these embodiments, menu data may besent 82 through a communications link 64 to an imaging device 30.Accordingly, menu data configured for display on an imaging device isstored on RCD 60.

An RCD 60, of some embodiments, will be further configured to receive 84user input obtained through the user interface 32 of an imaging device30 and transferred to the RCD 60 over communications links 38 & 64. Oncethis input data is received at an RCD 60, the input data may beprocessed 86. This processing 86 may comprise conversion of the data toa new format, execution of commands contained within the data or someother process. Once the input data has been processed 86, the processedoutput may be sent 88 back to the imaging device 30 where the processedoutput may be used in an imaging device process or function.

In some embodiments, as described with reference to FIG. 9, an RCD 60may send 90 menu data configured for an imaging device display 36 usinga markup language. The markup language menu data is then received at theimaging device 30 and displayed to a user. Typically, this will promptthe user to enter an input on the imaging device user interface 32. Thisuser input will then be sent by the imaging device 30 to the RCD 60. TheRCD 60 will then receive 92 the input data prompted by the display ofthe menu data on the imaging device 30. Once received, the input datamay be processed 94 on the RCD 60. Processing may comprise theselection, recordation and/or modification of a form, document or otherdata stored on RCD 60, the authorization of a user identified by theuser input, the translation of a document input by the user, generationof a map or other directions related to user input or some other processor function.

Some embodiments of the present invention may be described withreference to FIGS. 10 & 11. These embodiments comprise at least one RCD60 and a plurality of imaging devices 30 a-30 d. In these embodiments,at least one of the imaging devices 30 a-30 d comprises a user interface32 with a display 36 and user input panel 34 that is integral with thedisplay (i.e., touch-screen) or a separate input unit. RCD 60 isconnected to imaging devices 30 a-30 d by a communications link andnetwork 100 to enable data transmission between RCD 60 and imagingdevices 30 a-30 d.

In these embodiments, menu data is stored on RCD 60 and sent 110 to atleast one of the imaging devices 30 a-30 d where the menu data isdisplayed on a user interface. Any of Imaging devices 30 a-30 d thatreceive the menu data are configured to accept 112 and transmit 114 userinput to an RCD 60. Once the user input data is received at the RCD, thedata may be processed 116 as discussed in previously describedembodiments. The result of processing 116 may then be sent 118 back toany combination of the imaging devices 30 a-30d.

In these embodiments, a single RCD 60 may be used to provide processingpower, resources and functionality to a plurality of imaging devices 30a-30 d without reproducing these resources in each imaging device. Insome embodiments, data generated by input on one imaging device 30 a maybe directed to another imaging device 30 d for processed data output orfinal processing.

Some embodiments of the present invention may be described withreference to FIG. 12. In these embodiments, an imaging device (IDev) 120comprises a user interface 124, which is capable of receiving user inputand displaying data to a user. The user interface 124 will typicallycomprise a display, often in the form of a touch panel. The display maybe used to display data to a user. This data may comprise menu data toprompt for a user selection or data entry, such as a user ID andpassword, form selection or some other input. The imaging device 120 hasa communication link 122, which may comprise a typical computer networkconnection, a serial cable or some other wired or wireless communicationlink as described in other embodiments. The communication link 122 mayconnect the imaging device 120 to a remote computing device (RCD) 126 a,126 b, such as a server. The RCD 126 a, 126 b may be used to storedocuments, such as forms, and other data and make that data accessiblefrom the imaging device 120. The RCD 126 a, 126 b may also executeapplications that interact with or receive input from the imaging device120 and its user interface 124. In some embodiments, a database 125 maybe linked to the imaging device 120 and/or an RCD 126 a, 126 b. In someembodiments, an RCD 126 b or database 125 may be connected to an IDev120 over a wide area network such as the internet 128.

Some embodiments of the present invention may be described withreference to FIG. 13. In these embodiments, one or more imaging devices(IDev) 130 a-130 c, comprising user interfaces 134 a-134 c, which arecapable of receiving user input and displaying data to a user. The userinterfaces 134 a-134 c will typically comprise displays, often in theform of a touch panel. The displays may be used to display data 122 to auser. The imaging devices 130 a-130 c have a communication link 132,which may comprise a typical computer network connection, a serial cableor some other wired or wireless communication link as described in otherembodiments. The communication link 132 may connect the imaging devices130 a-130 c to one or mores remote computing devices (RCD) 136 a, 136 b,such as a server. The RCDs 136 a, 136 b may be used to store documents,such as forms, and other data and make that data accessible from theimaging devices 130 a-130 c. The RCDs 136 a, 136 b may also executeapplications that interact with or receive input from the imagingdevices 130 a-130 c and their user interfaces 134 a-134 c. In someembodiments, a database 135 may be linked to the imaging devices 130a-130 c and/or the RCDs 136 a, 136 b. In some embodiments, an RCD 136 bor database 135 may be connected to an IDev 130 a-130 c over a wide areanetwork such as the internet 138.

Concurrent Account Use Accounting Embodiments

Some embodiments of the present invention comprise methods and systemsthat provide for concurrent use of a peripheral device user account. Ina typical peripheral device system, concurrent use of the same useraccount by more than one user is not allowed. For example, in a typicalperipheral device accounting system, two users sharing a single accountcannot access devices that will charge fees to the same account duringthe same period of time. In current systems the first user to login isallowed to proceed with his job while the second is denied permission.

In known accounting systems for peripheral device access, only a singleuser may login to a user account at a time. Subsequent users must waituntil the first user has completed a job to commence any subsequentjobs. Typically, an imaging system will perform a requested job andthen, upon completion of that job, deduct the job amount from the useraccount. Because the job charges are not known in advance, multipleusers cannot use the same account as one user may deplete the accountfinds while multiple jobs are being executed. Consequently, knownsystems lack the ability to allow multiple users to login concurrentlyto the same account.

Embodiments of the present invention comprise methods and systems thathave the capability to calculate job charges before execution of the joband to deduct the charges from an account before execution of the job.Using these systems and methods allows multiple users to use an accountwithout the risk of exceeding account limits. Once account limits arereached, no further jobs will be authorized. A system with the abilityto allow multiple users sharing the same account to concurrently loginto multiple imaging devices and run multiple jobs simultaneously whilecharging the jobs to the same account can allow a group to operate moreefficiently and more profitably.

Embodiments of the present invention provide for multiple concurrentaccount users by calculating the charges associated with a proposedimaging job and deducting those charges from the account or otherwiseadjusting the account to account for the job charges. This is donebefore execution of the job so that account limits will not be exceededby other jobs that occur within the same period of time. In someembodiments, these job charges may be estimated. These estimates may beperformed conservatively and may result in an overcharge to the accountthat can be rectified after a more accurate job charge is calculated.Some embodiments may comprise systems and methods that perform a roughor conservative jog charge estimate that is deducted or otherwisesettled against the account. In these embodiments, a more accurate jobcharge may be calculated during or after execution of the job and themore accurate charge may result in a further adjustment to the account.While the account may be temporarily overcharged, account limits are notexceeded despite concurrent account use.

Some embodiments of the present invention may comprise limits on thenumber of concurrent account users. These limits may be related to theability of the system to accurately estimate the appropriate charges foran imaging job. When job charges cannot be accurately estimated, thenumber of concurrent users may be limited to a small number. When jobcharges can be estimated with extreme accuracy, a high number ofconcurrent users may be allowed. The accuracy of job charge estimatesmay be related to the specific type of imaging job. Some jobs, such asimage scanning to a file, may be accurately predicted without details ofthe actual document to be scanned while some jobs, such as colorcopying, may require pixel counts and detailed job parameters toaccurately estimate job charges. Because of these varying job chargeestimation factors, the accuracy of the total amount charged to anaccount may vary depending on the types of jobs in progress at anyperiod of time. To account for this estimated charge inaccuracy, thenumber of concurrent account users may be limited to a specific numberor may be limited to a variable number that is dependent on the types ofjobs currently in progress in the system. Accordingly, the number ofconcurrent account users may be limited to a fixed number or a variablenumber. This limit on the number of concurrent account users may be maybe affected by many factors and may or may not be related to theaccuracy of estimated job charges.

Some embodiments of the present invention comprise imaging jobconfiguration capabilities that define elements of an imaging job. Atypical multi-function peripheral (MFP) imaging device has thecapability to scan, print, fax and copy documents. Some MFPs may alsohave e-mail functions as well. Many MFPs allow a job to be configured ingreat detail. Scan or copy jobs may allow a user to zoom or magnify animage, crop the image, sharpen the image, modify color characteristicsand select many other features. Print and copy jobs may allow a user toselect color options, darkness levels, N-Up formatting, paper size andmany other features. Imaging jobs may be configured to comprise manyfunctions and elements.

Generally, an imaging job can be broken down into elemental functionsand processes that are accomplished by different parts of the imagingdevice. For example, a simple copy job can be broken down into a scanprocess and a print process. More complex copy jobs may comprisezooming, cropping, rotating, sharpening, page formatting and otherelemental functions. These elemental functions and their attributes maybe referred to as detailed job parameters. Detailed job parameterscomprise media type, media size, media quantity, quantity of impressionsper page, pixel count data, image resolution, finishing operations,stapling requirements, punching requirements, collating requirements,color attributes, color depth, color quantity, ink consumption, tonerconsumption, contrast media consumption, monochrome attributes,grey-scale attributes, double-sided characteristics, single-sidedcharacteristics, N-Up formatting, paper tray selection, scandestination, print destination, power consumption, job type (i.e.,print, copy, scan, facsimile, and document management) and many otherparameters.

In some embodiments of the present invention, job costs, fees and/orcharges may be calculated in relation to job configuration data and, insome embodiments, in relation to detailed job parameters as describedabove.

Some embodiments of the present invention may comprise an imaging device(IDev) in communication with one or more additional IDevs or one or moreremote computing devices (RCDs).

Some embodiments of the present invention may be described withreference to FIGS. 10, 12 & 14. These embodiments may comprise an IDev120, 30 a-30 d that is capable of receiving 140 account ID data from auser. This account ID data may be received directly from a user throughan UI on the IDev 120, 30 a-30 d. Account ID data may also betransmitted from a remote device that has received user input directly.Account ID data may also be received as a set of commands from anotherdevice in an automated system or from other sources. Once account IDdata is accepted the IDev 120, 30 a-30 d may receive job configurationdata from a user. This job configuration data may be received directlyfrom a user through an UI on the IDev 120, 30 a-30 d. Job configurationdata may also be transmitted from a remote device that has received userinput directly. Job configuration data may also be received as a 'set ofcommands from another device in an automated system or from othersources. Once this job configuration data is received, it may be sent142 to an RCD 60, 126 a-b for processing. An accounting applicationrunning on the RCD 60, 126 a-b may then calculate 144 job costs and feesfrom the job configuration data and/or detailed job parameters. Oncecosts, fees or charges are calculated for the job, they may then becompared 145 by the accounting application with accounting restrictionsand an account verification process may be employed whereby the fees forthe current job are compared to a user's account to verify 146 thatthere is sufficient account capacity. Account capacity may represent anamount of funds available in a debit account, an amount of creditavailable on a credit account or some other metric in an accountingsystem. Based on this account verification process 146, a job may beapproved 148 or denied 147.

When this determination has been made and the job configuration receivesaccounting approval the job amount may be deducted 148 from a useraccount prior to execution of the job. In these embodiments, the chargesfor the current job may be deducted by reducing an amount of fundsavailable in a debit account, decreasing an amount of credit availableon a credit account or adjusting some other metric in an accountingsystem. The IDev 120, 30 a-30 d may then execute 149 the job asconfigured. If the job configuration does not receive accountingapproval, the job request may be denied 147 and the job will not beexecuted.

In some exemplary embodiments, related to those depicted in FIG. 14, auser may login 140 to an imaging device using an account ID. A user mayalso read prompts in the form of text and graphics displayed on animaging device UI display. In response to these prompts, the user mayinput job configuration data using the IDev UI. A user may also inputdata directly without a prompting procedure. For example, a user mayselect a high-resolution, color, copy function that enlarges the imageby 100% and applies a filter to sharpen the image and finally prints theimage on photographic media paper. This input is accepted 141 by theIDev and sent to an accounting application for processing. The IDev maythen calculate 144 job costs using this job configuration data. Thecosts, fees or charges associated with the job may be compared withaccounting restrictions. In a debit account scenario, the user's accountmay be checked to verify 146 that funds have been deposited to cover thecost of the imaging job. If the account has sufficient funds, a job maybe approved 148 by the accounting system and the job amount deductedfrom the user account prior to the execution of the job. The imagingdevice may then proceed with execution 149 of the job as configured. Ifthe account does not have sufficient funds, the job will be denied 147and will not be allowed to execute on the imaging device.

Some embodiments of the present invention may be described withreference to FIGS. 10, 12 & 15. These embodiments may comprise an IDev120, 30 a-30 d that is capable of receiving 150 account ID data from auser as described above. Once account ID data is received, the IDev 120,30 a-30 d may 151 prompt for and/or receive job configuration data froma user. This job configuration data may be received directly from a userthrough an UI on the IDev 120, 30 a-30 d. Job configuration data mayalso be transmitted from a remote device that has received user inputdirectly. Job configuration data may also be received as a set ofcommands from another device in an automated system or from othersources. Once this job configuration data is received, it may be sent152 to an RCD 60, 126 a-b for processing. As in some other embodiments,an accounting application running on the RCD 60, 126 a-b may thencalculate 154 job costs, fees or charges based on the job configurationdata. In some embodiments, costs, fees or charges may be calculatedbased on detailed job parameters. Once costs and fees are calculated forthe job, they may then be compared 155, by the accounting application,with accounting restrictions and an account verification process may beemployed as described above. When this determination has been made, andthe job configuration receives accounting approval, the job charges maybe applied 158 to user account and the IDev 120, 30 a-30 d may executethe job 159 as configured. In some embodiments, if the job configurationdoes not receive accounting approval, the job may be reconfigured 157 toa configuration that meets accounting restrictions and the reconfiguredjob may be sent to the IDev 120, 30 a-30 d for execution. If the accountrestrictions will not allow the job 157, the IDev may modify the job, bylimiting a job parameter or by some other means, until the job costs orfees fall within accounting restrictions. For example, and not by way oflimitation, a job that has been configured for 50 copies may be limitedto 30 copies when a user's account only has sufficient funds to cover 30copies. As another non-limiting example, a job may be changed from colorcopies on photo paper to color copies on bond paper when this changewill bring the job into compliance with accounting restrictions.

Some embodiments of the present invention may be described withreference to FIGS. 10, 12 & 16. These embodiments comprise an IDev 120,30 a-30 d that is capable of receiving 160 account ID data from a useras described above. Once account ID data is received the IDev 120, 30a-30 d may 161 prompt for and/or receive job configuration data from auser. This job configuration data may be received directly from a userthrough an UI on the IDev 120, 30 a-30 d. Job configuration data mayalso be transmitted from a remote device that has received user inputdirectly. Job configuration data may also be received as a set ofcommands from another device in an automated system or from othersources. Once this job configuration data is received, it may be sent162 to an RCD 60, 126 a-b for processing. As in some other embodiments,an accounting application running on the RCD 60, 126 a-b may thencalculate 164 job costs, fees or charges based on the job configurationdata. Once costs, fees or charges are calculated for the job, they maythen be compared 166 by the accounting application with accountingrestrictions and an account verification process may be employed asdescribed above. When this determination has been made and the jobconfiguration receives accounting approval, the job charges may beapplied 168 to the user account and the IDev 120, 30 a-30 d may executethe job 169 as configured. In these embodiments, if account restrictionsare not met 167, a user may be prompted to modify the job configuration.This may be accomplished by input on an imaging device user interface.In some embodiments, the IDev may prompt the user with data indicatingwhich configuration characteristics may be changed to make the jobcomply with accounting restrictions.

Some embodiments of the present invention may be described withreference to FIGS. 10, 12 & 17. These embodiments comprise an IDev 120,30 a-30 d that is capable of receiving 170 account ID data. This accountID data may be received directly from a user through an UI on the IDev120, 30 a-30 d. Account ID data may also be transmitted from a remotedevice that has received user input directly. Account ID data may alsobe received as a set of commands from another device in an automatedsystem or from other sources. Once this account ID data is received 170,it may be sent 171 to an RCD 60, 126 a-b for processing. The RCD 60, 126a-b may process the data and determine whether the job complies withconcurrent user account restrictions. For example, and not by way oflimitation, an account with a concurrent user maximum set at three willnot allow a fourth concurrent user to login to the account. As anothernon-limiting example, an account with the concurrent user featuredisabled will not allow more than one user to login. If the concurrentuser limit is exceeded, a user will be denied 173 access to systemfunctions. When this determination has been made and the concurrentaccount user receives accounting approval the IDev 120, 30 a-30 d may174 prompt for job configuration data from a user as described above.Once this job configuration data is received, it may be sent 175 to anRCD 60, 126 a-b for processing. As in some other embodiments, anapplication running on the RCD 60, 126 a-b may then calculate 176 jobcosts, fees and charges from the job configuration data. Once costs,fees and charges are calculated for the job, the application may processthe data and determine whether the job complies with accountingrestrictions as described above. When this determination has been madeand the job configuration receives accounting approval, the job chargesmay be applied 178b to the user account as described above and the IDev120, 30 a-30 d may execute the job 179 as configured. If the job doesnot receive accounting approval, the job request may be denied 178 a andthe job will not be executed.

Some embodiments of the present invention may be described withreference to FIGS. 10, 12 & 18. These embodiments comprise an IDev 120,30 a-30 d that is capable of receiving 180 account ID data from a useras described above. Once this account ID data is received 180, it may besent 181 to an RCD 60, 126 a-b for processing. The RCD 60, 126 a-b mayprocess 182 the data and determine whether the job complies withconcurrent user account restrictions as described above. When thisdetermination has been made and the concurrent account user receivesaccounting approval the IDev 120, 30 a-30 d may prompt 184 for jobconfiguration data from user. This job configuration data may bereceived as described above. Once this job configuration data isreceived, it may be sent 185 to an RCD 60, 126 a-b for processing. As insome other embodiments, an application running on the RCD 60, 126 a-bmay then calculate 186 job costs, fees and charges from the jobconfiguration data. Once costs, fees and charges are calculated for thejob, the application may process the data and determine whether the jobcomplies with accounting restrictions 187. When this determination hasbeen made and the job configuration receives accounting approval, thejob charges may be applied 188 b to the user account and the IDev 120,30 a-30 d may execute the job 189 as configured. In some embodiments, ifthe job configuration does not receive accounting approval, the job maybe reconfigured 188 a to a configuration that meets accountingrestrictions and the reconfigured job may be sent to the IDev 120, 30a-30 d for execution. If the account restrictions will not allow the job188 a, the IDev may modify the job, by limiting a job parameter or bysome other means, until the job costs, fees or charges fall withinaccounting restrictions. For example, and not by way of limitation, ajob that has been configured for 50 copies may be limited to 30 copieswhen a user's account only has sufficient finds to cover 30 copies. Asanother non-limiting example, a job may be changed from color copies onphoto paper to color copies on bond paper when this change will bringthe job into compliance with accounting restrictions.

Some embodiments of the present invention may be described withreference to FIGS. 10, 12 & 19. These embodiments comprise an IDev 120,30 a-30 d that is capable of receiving 190 account ID data from a useras described above. Once this account ID data is received 190, it may besent 191 to an RCD 60, 126 a-b for processing. The RCD 60, 126 a-b mayprocess 192 the data and determine whether the job complies withconcurrent user account 30 restrictions as described above. When thisdetermination has been made and the concurrent account user receivesaccounting approval the IDev 120, 30 a-30 d may prompt 194 for jobconfiguration data from user. This job configuration data may bereceived as described above. Once this job configuration data isreceived, it may be sent 195 to an RCD 60, 126 a-b for processing. As insome other embodiments, an application running on the RCD 60, 126 a-bmay then calculate 196 job costs, fees and charges from the jobconfiguration data. Once costs, fees and charges are calculated for thejob, the application may process the data and determine whether the jobcomplies with accounting restrictions 197. When this determination hasbeen made and the job configuration receives accounting approval, thejob charges may be applied 198 b to the user account and the IDev 120,30 a-30 d may execute the job 199 as configured. In these embodiments,if account restrictions are not met, a user may be prompted 198 a tomodify the job configuration. This may be accomplished by input on animaging device user interface. In some embodiments, the IDev may promptthe user with data indicating which configuration characteristics may bechanged to make the job comply with accounting restrictions.

Some embodiments of the present invention, illustrated in FIG. 20,comprise an IDev 120, 30 a-30 d that is capable of receiving 200 accountID data from a user as described above. Once account ID data is acceptedthe IDev 120, 30 a-30 d may receive 201 job configuration data. This jobconfiguration data may be received as described above in relation toother embodiments. Once this job configuration data is received, it maybe sent 202 to an RCD 60, 126 a-b for processing. As in some otherembodiments, an accounting application running on the RCD 60, 126 a-bmay then calculate 203 job costs, fees and charges from the jobconfiguration data. Once costs, fees and charges are calculated for thejob, they may then be compared 204 by the accounting application withaccounting restrictions. When this determination has been made and thejob configuration receives accounting approval, the job charges may beapplied 205 b to the user account and the IDev 120, 30 a-30 d mayexecute the job 206 as configured. If the job configuration does notreceive accounting approval, the job request may be denied 205 a and thejob will not be executed.

During processing of the job many things can occur that may give thesystem additional data to better calculate job costs, fees and charges.Additionally, errors may occur that may change the outcome of a job andits associated costs, fees and charges. For example, the cost of tonerfor a particular imaging job may be estimated the initial calculation ofjob costs, fees and charges. Once the job has completed, the system mayhave the capability to measure the exact amounts of toners used tocomplete the job. When there is a significant difference between theoriginally calculated costs, fees or charges and the post-job-executioncalculations for job costs, fees or charges, adjustments may be made tothe account to reflect the more accurate costs, fees or charges.

Errors may also occur during processing of an imaging job. These errorsmay affect the final job product such that it differs from what the useroriginally configured. For example, a paper jam may occur when a job ispartially complete. Without manual intervention, the job will terminatewithout completion. When this occurs, the job costs, fees and chargesmay be recalculated to reflect the costs, fees and charges of theportion of the job that is complete.

Consequently, some embodiments of the present invention comprise systemsand methods for calculating the costs, fees or charges of a specific jobonce the job has been completed and adjusting the costs, fees andcharges applied to a user account after completion of a job. The resultsof these calculations may be reflected in a job result report. The term“job results” comprises the results of these calculations as well asother data related to an imaging job and its execution.

In these embodiments, the IDev, 120, 30 a-30 d may send job results 207to an RCD 60, 126 a-b for processing. In these embodiments, anaccounting application running on the RCD 60, 126 a-b may determine ifthe job was completed successfully and within accounting parameters. Ifthe job was not completed successfully or if an accounting parameterexceeded its limits, the application may adjust the costs, fees orcharges applied to the user's account. For example, and not by way oflimitation, if a job that has been configured for 50 copies and thesystem only completes 25 copies before the device depletes its papersupply, the application may refund the amount for 25 copies back touser's account. As another non-limiting example, if a job has beenconfigured for 20 copies and the system only completes 10 before thetoner is depleted, the application may refund the costs, fees or chargesassociated with the 10 pages that were not completed. As an additionalnon-limiting example, a job may be configured for a fixed number ofpages of color copies. Before job execution, the job costs, fees orcharges are calculated using estimated amounts of toners. These costs,fees or charges are then applied to the user's account prior to jobexecution. During or after job execution, the actual amounts of tonersmay be measured accurately and the actual costs, fees or charges may bevery accurately calculated. In this example, the costs, fees or chargesbased on the actual job consumption are significantly lower than theestimated costs, fees or charges applied to the account beforeexecution. In this situation, the difference between the initial andsubsequent charges is refunded to the user's account.

In these embodiments, when the initial costs, fees or charges differsignificantly from the more accurate costs, fees or charges calculatedduring or after job completion, an adjustment may be applied 208 to theuser's account to reflect this difference. This adjustment may take theform of a refund, an additional charge or some other adjustment. When nosignificant difference is calculated, the process may terminate 209without further adjustment.

Further embodiments of the present invention may be described withreference to FIGS. 10, 12 & 21. These embodiments comprise an IDev 120,30 a-30 d that is capable of receiving 210 account ID data from a user.Once account ID data is accepted, the IDev 120, 30 a-30 d may prompt 211for job configuration data from a user. This job configuration data maybe received as described above. Once this job configuration data isreceived, it may be sent 212 to an RCD 60, 126 a-b for processing. As insome other embodiments, an accounting application running on the RCD 60,126 a-b may then calculate 213 job costs, fees or charges from the jobconfiguration data. Once costs, fees or charges are calculated for thejob, they may then be compared 214, by the accounting application, withaccounting restrictions as described above. When this determination hasbeen made and the job configuration receives accounting approval, thejob charges may be applied 215 b to the user account and the IDev 120,30 a-30 d may execute the job 216 as configured. In some embodiments, ifthe job configuration does not receive accounting approval, the job maybe automatically reconfigured 215 a to a configuration that meetsaccounting restrictions, as described above, and sent to the IDev 120,30 a-30 d for execution.

In some of these embodiments, the IDev, 120, 30 a-30 d may send 217 jobresults to an RCD 60, 126 a-b for processing. In these embodiments, anaccounting application running on the RCD 60, 126 a-b may determine,through the use of the job results, if the job was completedsuccessfully and within accounting parameters. If the job was notcompleted successfully and/or was not completed within accountingparameters, the application may then adjust the user's account 218 toaccount for the difference in costs, fees or charges. If the job isfound to have been completed successfully and within accountingparameters, the process may continue without further adjustment 219.

Further embodiments of the present invention may be described withreference to FIGS. 10, 12 & 22. These embodiments comprise an IDev 120,30 a-30 d that is capable of receiving 220 account ID data from a user.Once account ID data is accepted, the IDev 120, 30 a-30 d may prompt 221for job configuration data from a user. This job configuration data maybe received as described above. Once this job configuration data isreceived, it may be sent 222 to an RCD 60, 126 a-b for processing. As insome other embodiments, an accounting application running on the RCD 60,126 a-b may then calculate 223 job costs, fees or charges from the jobconfiguration data. Once costs, fees or charges are calculated for thejob, they may then be compared 224, by the accounting application, withaccounting restrictions as described above. When this determination hasbeen made and the job configuration receives accounting approval, thejob charges may be applied 225 b to the user account and the IDev 120,30 a-30 d may execute the job 226 as configured. In some embodiments, ifthe job configuration does not receive accounting approval, a user maybe prompted 225 a to modify the job configuration. This may beaccomplished by input on an imaging device user interface. In someembodiments, the IDev may prompt the user with data indicating whichconfiguration characteristics may be changed to make the job comply withaccounting restrictions.

In some of these embodiments, the IDev, 120, 30 a-30 d may send 227 jobresults to an RCD 60, 126 a-b for processing. In these embodiments, anaccounting application running on the RCD 60, 126 a-b may determine,through the use of the job results, if the job was completedsuccessfully and within accounting parameters. If the job was notcompleted successfully and/or was not completed within accountingparameters, the application may then adjust the user's account 228 anyover-deducted amount to the user's account as described above. If thejob is found to have been completed successfully and within accountingparameters, the process may continue without further adjustment 229.

Some embodiments of the present invention may be described withreference to FIGS. 10, 12 & 23. These embodiments comprise an IDev 120,30 a-30 d that is capable of receiving 230 account ID data from a useras described above in relation to other embodiments. Once this accountID data is received 230, it may be sent 231 to an RCD 60, 126 a-b forprocessing. The RCD 60, 126 a-b may process 232 the data and determinewhether the job complies with concurrent user account restrictions asdescribed above. When this determination has been made and theconcurrent account user receives accounting approval, the IDev 120, 30a-30 d may prompt 232 b for job configuration data from a user. This jobconfiguration data may be received as described above. Once this jobconfiguration data is received, it may be sent 233 to an RCD 60, 126 a-bfor processing. When concurrent user parameters are not met, the job maybe denied 232 a.

As in some other embodiments, an accounting application running on theRCD 60, 126 a-b may then calculate 234 job costs, fees or charges fromthe job configuration data. Once costs, fees or charges are calculatedfor the job, they may then be compared 235 by the accounting applicationwith accounting restrictions and an account verification process may beemployed as described above. When this determination has been made andthe job configuration receives accounting approval, the job costs, feesor charges may be applied 235 b to the user account. The IDev 120, 30a-30 d may then execute the job 236 as configured. In some embodiments,if the job configuration does not receive accounting approval, the jobrequest may be denied 235 a.

In some embodiments, the IDev, 120, 30 a-30 d may send 237 job resultsto an RCD 60, 126 a-b for processing. An accounting application runningon the RCD 60, 126 a-b may then determine if the job was completedsuccessfully and within accounting parameters. If the job was notcompleted successfully or if an accounting parameter exceeded itslimits, the application may adjust 238 the costs, fees or chargesapplied to the user's account. The process may continue 239 withoutfurther adjustment when the job is completed successfully and withinaccounting parameter limits.

Some embodiments of the present invention may be described withreference to FIGS. 10, 12 & 24. These embodiments comprise an IDev 120,30 a-30 d that is capable of receiving 240 account ID data from a useras described above in relation to other embodiments. Once this accountID data is received 240, it may be sent 241 to an RCD 60, 126 a-b forprocessing. The RCD 60, 126 a-b may process 242 the data and determinewhether the job complies with concurrent user account restrictions asdescribed above. When this determination has been made and theconcurrent account user receives accounting approval, the IDev 120, 30a-30 d may prompt 242 b for job configuration data from a user. This jobconfiguration data may be received as described above. Once this jobconfiguration data is received, it may be sent 243 to an RCD 60, 126 a-bfor processing. When concurrent user parameters are not met, the job maybe denied 242 a and further processing may cease.

As in some other embodiments, an accounting application running on theRCD 60, 126 a-b may then calculate 244 job costs, fees or charges fromthe job configuration data. Once costs, fees or charges are calculatedfor the job, they may then be compared 245 by the accounting applicationwith accounting restrictions and an account verification process may beemployed as described above. When this determination has been made andthe job configuration receives accounting approval, the job costs, feesor charges may be applied 245 b to the user account. The IDev 120, 30a-30 d may then execute the job 246 as configured.

In some embodiments, if the job configuration does not receiveaccounting approval, the job request may be automatically reconfigured245 a to a configuration that meets accounting restrictions and sent tothe IDev 120, 30 a-30 d for execution.

In some embodiments, the IDev, 120, 30 a-30 d may send 247 job resultsto an RCD 60, 126 a-b for processing. An accounting application runningon the RCD 60, 126 a-b may then determine if the job was completedsuccessfully and within accounting parameters. If the job was notcompleted successfully or if an accounting parameter exceeded itslimits, the application may adjust 248 the costs, fees or chargesapplied to the user's account. The process may continue 249 withoutfurther adjustment when the job is completed successfully and withinaccounting parameter limits.

Some embodiments of the present invention may be described withreference to FIGS. 10, 12 & 25. These embodiments comprise an IDev 120,30 a-30 d that is capable of receiving 250 account ID data from a useras described above in relation to other embodiments. Once this accountID data is received 250, it may be sent 251 to an RCD 60, 126 a-b forprocessing. The RCD 60, 126 a-b may process 252 the data and determinewhether the job complies with concurrent user account restrictions asdescribed above. When this determination has been made and theconcurrent account user receives accounting approval, the IDev 120, 30a-30 d may prompt 252 b for job configuration data from a user. This jobconfiguration data may be received as described above. Once this jobconfiguration data is received, it may be sent 253 to an RCD 60, 126 a-bfor processing. When concurrent user parameters are not met, the job maybe denied 252 a and further processing may cease.

As in some other embodiments, an accounting application running on theRCD 60, 126 a-b may then calculate 254 job costs, fees or charges fromthe job configuration data. Once costs, fees or charges are calculatedfor the job, they may then be compared 255 by the accounting applicationwith accounting restrictions and an account verification process may beemployed as described above. When this determination has been made andthe job configuration receives accounting approval, the job costs, feesor charges may be applied 255 b to the user account. The IDev 120, 30a-30 d may then execute the job 256 as configured.

In these embodiments, if account restrictions are not met, a user may beprompted 255 a to modify the job configuration. This may be accomplishedby input on an imaging device user interface. In some embodiments, theIDev may prompt the user with data indicating which configurationcharacteristics may be changed to make the job comply with accountingrestrictions.

In some embodiments, the IDev, 120, 30 a-30 d may send 257 job resultsto an RCD 60, 126 a-b for processing. An accounting application runningon the RCD 60, 126 a-b may then determine if the job was completedsuccessfully and within accounting parameters. If the job was notcompleted successfully or if an accounting parameter exceeded itslimits, the application may adjust 258 the costs, fees or chargesapplied to the user's account. The process may continue 259 withoutfurther adjustment when the job is completed successfully and withinaccounting parameter limits.

The terms and expressions which have been employed in the forgoingspecification are used therein as terms of description and not oflimitation, and there is no intention in the use of such terms andexpressions of excluding equivalence of the features shown and describedor portions thereof, it being recognized that the scope of the inventionis defined and limited only by the claims which follow.

1. A method for enabling use of an imaging device account by multiple concurrent users, said method comprising: a) receiving, at a remote computing device (RCD), a user account identification (ID) from an imaging device for an imaging device account; b) receiving job configuration data for an imaging job at said RCD from said imaging device; c) calculating job charges at said RCD using said job configuration data; d) verifying that said job charges meet accounting restrictions for said account; e) applying said job charges to said account prior to authorization of said job; and f) authorizing said imaging device to execute said job when said job charges meet said accounting restrictions.
 2. A method as described in claim 1 further comprising: automatically modifying said job configuration to meet accounting restrictions when said job charges do not meet accounting restrictions; recalculating said job charges based on said modified job configuration; applying said recalculated job charges to said account prior to authorizing said modified job; and authorizing said modified job.
 3. A method as described in claim 1 further comprising: prompting a user to modify said job configuration when said job charges do not meet accounting restrictions; receiving a modified job configuration that meets accounting restrictions; recalculating job charges based on said modified job configuration; applying said recalculated job charges to said account prior to authorization of said modified job; and authorizing said modified job.
 4. A method as described in claim 1 further comprising determining whether said job was completed successfully and adjusting said job charges applied to said account to account for any unsuccessful job completion.
 5. A method as described in claim 1 further comprising determining whether said job charges are accurate based on data obtained after commencement of job execution and adjusting said job charges applied to said account to account for any inaccuracy in the initial calculation of said job charges.
 6. A method as described in claim 1 further comprising an initial step of determining whether a concurrent user limit will be exceeded by the addition of another user and denying any further account access or authorization when said limit will be exceeded.
 7. A system for enabling use of an imaging device account by multiple concurrent users, said system comprising: a) a receiver for receiving, at a remote computing device (RCD), a user account identification (ID) from an imaging device for an imaging device account; b) said receiver also being capable of receiving job configuration data for an imaging job at said RCD from said imaging device; c) a calculator for calculating job charges at said RCD using said job configuration data; d) an accounting manager for verifying that said job charges meet accounting restrictions for said account; e) said accounting manager also being capable of applying said job charges to said account prior to authorization of said job; and f) an account authority for authorizing said imaging device to execute said job when said job charges meet said accounting restrictions.
 8. A system as described in claim 7 further comprising: a job modifier for automatically modifying said job configuration to meet accounting restrictions when said job charges do not meet accounting restrictions; a re-calculator for recalculating said job charges based on said modified job configuration; and a modified account manager for applying said recalculated job charges to said account before execution of said job.
 9. A system as described in claim 7 wherein said UI receiver is configured for prompting a user to modify said job configuration when said job charges do not meet accounting restrictions and for receiving a modified job configuration that meets accounting restrictions and wherein said calculator is also configured for recalculating job charges based on said modified job configuration and wherein said account manager is further configured for applying said recalculated job charges to said account prior to executing said job.
 10. A system as described in claim 7 further comprising a job analyzer for determining whether said job was completed successfully and wherein said account manager is further configured for adjusting said job charges applied to said account to account for any unsuccessful job completion.
 11. A system as described in claim 7 further comprising an accuracy analyzer for determining whether said job charges are accurate based on data obtained after commencement of job execution and wherein said account manager is configured for adjusting said job charges applied to said account to account for any inaccuracy in the initial calculation of said job charges.
 12. A system as described in claim 7 further comprising a concurrent user limiter for determining whether a concurrent user limit will be exceeded by the addition of another user and for denying any further account access or authorization when said limit will be exceeded.
 13. A method for enabling use of an imaging device account by multiple concurrent users, said method comprising: a) receiving, at a remote computing device (RCD), a user account identification (ID) from an imaging device for an imaging device account; b) verifying the concurrent user limit for said account and granting account access for said imaging device when said access will not exceed said concurrent user limit; c) receiving job configuration data for an imaging job at said RCD from said imaging device; d) calculating initial job charges at said RCD using said job configuration data; e) verifying that said initial job charges meet accounting restrictions for said account; f) applying said initial job charges to said account prior to authorization of said job when said initial job charges meet said accounting restrictions; g) authorizing said imaging device to execute said job when said initial job charges meet said accounting restrictions; h) providing for modification of said job when said job charges do not meet said accounting restrictions; i) recalculating said job charges based on said modification when said job charges do not meet said accounting restrictions; j) applying said modified job charges to said account when said initial job charges do not meet said accounting restrictions; and k) sending said modified job to said imaging device for execution on said imaging device.
 14. A method as described in claim 13 wherein said providing for modification of said job comprises automatically modifying said job configuration to meet accounting restrictions when said job charges do not meet accounting restrictions.
 15. A method as described in claim 13 wherein said providing for modification of said job comprises prompting a user to modify said job configuration when said job charges do not meet accounting restrictions.
 16. A method as described in claim 13 further comprising determining whether said job was completed successfully and adjusting said job charges applied to said account to account for any unsuccessful job completion.
 17. A method as described in claim 13 further comprising determining whether said job charges are accurate based on data obtained after commencement of job execution and adjusting said job charges applied to said account to account for any inaccuracy in the initial calculation of said job charges. 